Repository navigation
Release 0.6.0: PyPI package, build provenance and CI - #15
Merged
Merged
Conversation
- python/: wheels that ship the release binaries (maldoctrace command and a small Python API), built with the standard library only - release.yml: build provenance attestations for the archives and a PyPI job using trusted publishing; actions pinned by commit SHA - ci.yml: gofmt, vet, tests, short fuzzing and a wheel smoke test on every PR - SECURITY.md and Dependabot configuration - Version 0.6.0 in analyze.go, CHANGELOG, README and the Debian packaging
A compound file header can declare billions of FAT or mini FAT sectors; the parser pre-allocated buffers from those counts and a crafted file crashed the process with an out-of-memory error. Found by the new CI fuzzing job; the crashing input is kept as a regression case.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the 0.6.0 release. No analyzer code changes beyond the version string; the new features are the ones already in
[Unreleased](OneNote chains, VBScript emulation, batch deobfuscation, ISO/MSI/CHM).PyPI (
pip install maldoctrace)python/build_wheels.pywraps the six release binaries in platform wheels (win amd64/arm64, manylinux+musllinux x86_64/aarch64, macOS 11 x86_64/arm64). The binary is installed as themaldoctracecommand;maldoctrace.analyze()/analyze_bytes()return the JSON report as a dict.pypijob inrelease.yml, after the GitHub Release, publishing with trusted publishing from thepypienvironment (no token stored).twine check; the Windows and Linux (WSL) wheels install in a venv,maldoctrace versionprints 0.6.0 andanalyze()returns malicious/100 on the IcedID OneNote sample.Release hardening
gh attestation verify).CI / project hygiene
ci.yml: gofmt, vet, tests, 30 s fuzzing on six parsers, and a wheel build + install smoke test on every PR.SECURITY.md(private reporting through GitHub) and Dependabot for Go modules and actions.Before tagging v0.6.0: the PyPI pending publisher must exist (project
maldoctrace, workflowrelease.yml, environmentpypi).